Node-RED block in Snap4City Microservice library node-red-contrib-snap4city-user is "orion-out-api-v2">
	<p>Provides a node for sending generic json payload to Fiware Orion context broker Version 2.</p>
	
	<h3>Configuration</h3>
	<dl class="message-properties">
	
		<dt>Service</dt>	
		<dd>The URL and port of the Fiware Orion context broker (<b>mandatory</b>). 
		</dd>
		
		<dt>Certificates</dt>	
		<dd>Configuration for TLS connections (optional). If "verify server certificate" is selected, the CA certificate is <b>mandatory</b>
		</dd>
	
		<dt>Device Type
			<span class="property-type">string</span>
		</dt>
		<dd>Context element entity type (optional)</dd>
		
		<dt>Device Identifier
			<span class="property-type">string</span>
		</dt>
		<dd>Context element entity id (optional)</dd>	
		
		<dt>key 1
			<span class="property-type">string</span>
		</dt>
		<dd>K1 credential to be specified for context broker secured via Snap4City-OrionFilter (optional). It can be passed in <code>msg.auth.k1</code>
		(see example below)</dd>
		
		<dt>key 2
			<span class="property-type">string</span>
		</dt>
		<dd>K2 credential to be specified for context broker secured via Snap4City-OrionFilter (optional). It can be passed in <code>msg.auth.k2</code> (see example below)</dd>
		
		<dt>Service/Tenant
			<span class="property-type">string</span>
		</dt>
		<dd>Tenant of the Device to be specified if the context broker support Multi-Tenancy (optional)</dd>
		
		<dt>Service Path
			<span class="property-type">string</span>
		</dt>
		<dd>Service Path of the Device to be specified if the context broker support Multi-Tenancy/Service Path hierarchy (optional)</dd>	
		
		<dt>apikey
			<span class="property-type">string</span>
		</dt>
		<dd>Credential to be specified for context broker secured via HTTP Header "apikey:&lt;credential&gt;" (optional). It can be passed in <code>msg.auth.apikey</code> (see example below)</dd>
		
		<dt>auth
			<span class="property-type">string</span>
		</dt>
		<dd>Credential to be specified for context broker secured via HTTP Header "Authorization: &lt;credential&gt;" (optional). It can be passed in <code>msg.auth.basicAuth</code> (see example below)
		If this parameter is not specified, the Snap4City SSo AccessToken will be used (based on (cloud scenario) 
		the logged user credentials or (edge scenario) the specified username/password) in the form of "Authorization: Bearer &lt;credential&gt;"</dd>
		
		<dt>name
			<span class="property-type">string</span>
		</dt>
		<dd>Label assigned to the current node (optional)</dd>
	</dl>
	
	<h3>Inputs</h3>
	<dl class="message-properties">
		A JSON representing the payload to send to the Fiware Orion context broker. Can be:
		<ul>
			<li>the complete contextElements (not an array):
				<code>
					msg.payload ={"id":"test-edge-device","type":"test-edge-device","temperature":{"value":"14","type":"float"},"noise":{"value":"14","type":"integer"}};
				</code></br>
				NOTE: if msg.payload.type and msg.payload.id are not present, the "Device Type" and "Device Identifier" has to be specified in the Configuration section (<b>mandatory</b>)</li>
			<li>the simple attributes (an array)
				<code>
					msg.payload = [{"temperature":{"value":"16","type":"float"},"noise":{"value":"16","type":"integer"}}];
				</code></br>
				NOTE: the "Device Type" and "Device Identifier" has to be specified in the Configuration section (<b>mandatory</b>)</li>
		</ul>
		An optional JSON representing the set of Credentials (used just if not specified in UI)
		<code>
			msg.auth={"k1": "1ef0e5e8-bf0c-48d4-9462-0aa4cfcf5e19","k2": "b2b34425-9d97-4fc5-818d-2d6cac2314a6","apikey":"apikey","basicAuth": "basicAuthKey"};
		</code>
    </dl>
	
    <h3>Details</h3>
	<dl class="message-properties">	
		<p>The node receive a JSON as described in the Inputs section and send a message to the Fiware Broker context broker based on the specified Configuration.
			If the values are not present in the input JSON an error is generated.</p>
	</dl>